Background operations in memory

ABSTRACT

The present disclosure includes apparatuses and methods related to performing background operations in memory. A memory device can be configured to perform background operations while another memory device in a memory system and/or on a common memory module is busy performing commands received from a host coupled to the memory system and/or common memory module. An example apparatus can include a first memory device, wherein the first memory device can include an array of memory cells and a controller configured to perform a background operation on the first memory device in response to detecting a command from a host to a second memory device.

PRIORITY INFORMATION

This application is a Continuation of U.S. application Ser. No.16/290,110 filed Mar. 1, 2019, which issues as U.S. Pat. No. 10,789,015on Sep. 29, 2020, the contents of which are included herein byreference.

TECHNICAL FIELD

The present disclosure relates generally to memory devices, and moreparticularly, to apparatuses and methods for performing backgroundoperations in memory.

BACKGROUND

Memory devices are typically provided as internal, semiconductor,integrated circuits in computers or other electronic devices. There aremany different types of memory including volatile and non-volatilememory. Volatile memory can require power to maintain its data andincludes random-access memory (RAM), dynamic random access memory(DRAM), and synchronous dynamic random access memory (SDRAM), amongothers. Non-volatile memory can provide persistent data by retainingstored data when not powered and can include NAND flash memory, NORflash memory, read only memory (ROM), Electrically Erasable ProgrammableROM (EEPROM), Erasable Programmable ROM (EPROM), and resistance variablememory such as phase change random access memory (PCRAM), resistiverandom access memory (RRAM), and magnetoresistive random access memory(MRAM), among others.

Memory is also utilized as volatile and non-volatile data storage for awide range of electronic applications. Non-volatile memory may be usedin, for example, personal computers, portable memory sticks, digitalcameras, cellular telephones, portable music players such as MP3players, movie players, and other electronic devices. Memory cells canbe arranged into arrays, with the arrays being used in memory devices.

Memory can be part of a memory module (e.g., a dual in-line memorymodule (DIMM)) used in computing devices. Memory modules can includevolatile, such as DRAM, for example, and/or non-volatile memory, such asFlash memory or RRAM, for example. The DIMMs can be uses as main memoryin computing systems.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram of an apparatus in the form of a computingsystem including a memory system in accordance with a number ofembodiments of the present disclosure.

FIG. 1B is a block diagram of an apparatus in the form of a dual in-linememory modules (DIMM) in accordance with a number of embodiments of thepresent disclosure.

FIG. 2 is a block diagram of a computing system including a host and amemory system comprising a dual in-line memory module (DIMM) with portsin accordance with a number of embodiments of the present disclosure.

FIG. 3 is a block diagram of a computing system including a host and amemory system comprising a dual in-line memory module (DIMM) with aready/busy bus in accordance with a number of embodiments of the presentdisclosure.

FIG. 4 is a block diagram of a computing system including a host and amemory system comprising a dual in-line memory module (DIMM) with afirst and second controller in accordance with a number of embodimentsof the present disclosure.

FIG. 5 is a block diagram of a computing system including a host and amemory system comprising a dual in-line memory module (DIMM) with afirst and second controller and a first and second ready/busy bus inaccordance with a number of embodiments of the present disclosure.

FIG. 6 is a block diagram of a controller including backgroundoperations and a time calculator in accordance with a number ofembodiments.

FIG. 7 is a flow diagram illustrating an example of performing abackground operation on a memory device in accordance with a number ofembodiments of the present disclosure.

DETAILED DESCRIPTION

The present disclosure includes apparatuses and methods related toperforming background operations in memory. An example apparatus caninclude a first memory device, wherein the first memory device includesan array of memory cells and a controller configured to perform abackground operation on the first memory device in response to detectinga command from a host to a second memory device.

In a number of embodiments, the controller can perform backgroundoperations on the DIMM. For example, the controller can be configured toperform a background operation on a memory device of the DIMM. Thecontroller can perform the background operation on the memory device inresponse to the memory device being idle. The memory device can be idlewhen the memory device is not executing a command from the host, forexample.

In some examples, the controller can perform the background operation onthe memory device in response to the host sending non-target commandsand/or when non-target commands are being executed. For example, anon-target command can be a command to a different device that is notthe memory device. The command can be directed to a different device toperform a read operation and the memory device can perform a backgroundoperation in response to the host sending the command to the differentdevice, for example.

A memory system can include a dual in-line memory module (DIMM) having anumber of memory devices. For example, a DIMM can be a non-volatile DIMM(NVDIMM) that includes a number of volatile memory devices and a numberof non-volatile memory devices. A DIMM can execute commands to transferdata between the host and the volatile memory device, between the hostand the non-volatile memory device, between the volatile andnon-volatile memory devices, between non-volatile memory devices, andbetween volatile memory devices. The commands can be received by theDIMM from another device, such as a host, and/or can be generated by acontroller on the DIMM.

For example, the number of volatile memory devices can be coupled toanother device, such as a host, via a first port (e.g., a A Side Port)and be coupled to a controller on the DIMM via a second port (e.g., a BSide Port). The number of non-volatile memory devices can be coupled tothe controller on the DIMM. The DIMM can execute commands to transferdata between another device, such as a host, and the volatile memorydevices via a A Side Port and the DIMM can execute commands to transferdata between the volatile memory devices and the non-volatile memorydevices via a B Side Port. The DIMM can execute the commands to transferdata between another device and the volatile memory devices whileexecuting the commands to transfer data between the volatile memorydevice and the non-volatile memory devices.

The DIMM can include a number of embodiments where a port is not used tocouple the volatile memory devices to other devices and/or thecontroller (e.g., a bus from a host and/or controller is coupleddirectly to the volatile memory devices). The DIMM can send a ready/waitsignal to another device, such as a host, indicating whether or not theDIMM is ready to receive commands from the another device. For example,the DIMM can send a ready/wait signal to a host indicating the DIMM isnot ready to receive commands from the host and is busy executingcommands to transfer data between the memory devices on the DIMM. TheDIMM can send a ready/wait signal to a host indicating the DIMM is readyto receive commands from the host when the DIMM is not busy executingcommands to transfer data between the memory device on the DIMM.

In the following detailed description of the present disclosure,reference is made to the accompanying drawings that form a part hereof,and in which is shown by way of illustration how a number of embodimentsof the disclosure may be practiced. These embodiments are described insufficient detail to enable those of ordinary skill in the art topractice the embodiments of this disclosure, and it is to be understoodthat other embodiments may be utilized and that process, electrical,and/or structural changes may be made without departing from the scopeof the present disclosure. As used herein, the designator “N” indicatesthat a number of the particular feature so designated can be includedwith a number of embodiments of the present disclosure.

As used herein, “a number of” something can refer to one or more of suchthings. For example, a number of memory devices can refer to one or moreof memory devices. Additionally, designators such as “N”, as usedherein, particularly with respect to reference numerals in the drawings,indicates that a number of the particular feature so designated can beincluded with a number of embodiments of the present disclosure.

The figures herein follow a numbering convention in which the firstdigit or digits correspond to the drawing figure number and theremaining digits identify an element or component in the drawing.Similar elements or components between different figures may beidentified by the use of similar digits. As will be appreciated,elements shown in the various embodiments herein can be added,exchanged, and/or eliminated so as to provide a number of additionalembodiments of the present disclosure. In addition, the proportion andthe relative scale of the elements provided in the figures are intendedto illustrate various embodiments of the present disclosure and are notto be used in a limiting sense.

FIG. 1A is a functional block diagram of a computing system 100including an apparatus in the form of a number of memory systems 104-1 .. . 104-N, in accordance with one or more embodiments of the presentdisclosure. As used herein, an “apparatus” can refer to, but is notlimited to, any of a variety of structures or combinations ofstructures, such as a circuit or circuitry, a die or dice, a module ormodules, a device or devices, or a system or systems, for example. Inthe embodiment illustrated in FIG. 1A, memory systems 104-1 . . . 104-Ncan include a one or more dual in-line memory modules (DIMM) 110-1, . .. , 110-X, 110-Y. The DIMMs 110-1, . . . , 110-X, 110-Y can includevolatile memory and/or non-volatile memory. In a number of embodiments,memory systems 104-1, . . . , 104-N can include a multi-chip device. Amulti-chip device can include a number of different memory types and/ormemory modules. For example, a memory system can include non-volatile orvolatile memory on any type of a module. The examples described below inassociation with FIGS. 1A-7 use a DIMM as the memory module, but theembodiments of the present disclosure can be used on any memory systemthat include volatile and/or non-volatile memory. In FIG. 1A, memorysystem 104-1 is coupled to the host via channel 103-1 can include DIMMs110-1, . . . , 110-X, where DIMM 110-1 is a NVDIMM and 110-X is DRAMDIMM. In this example, each DIMM 110-1, . . . , 110-X, 110-Y includes acontroller 114. Controller 114 can receive commands from host 102 andcontrol execution of the commands on a DIMM. Also, in a number ofembodiments, the protocol of the present disclosure could be implementedby a memory device (e.g., a DIMM) without a controller and execution ofthe commands using the protocol of the present disclosure could be builtinto the memory device. The host 102 can send commands to the DIMMs110-1, . . . , 110-X, 110-Y using the protocol of the present disclosureand/or a prior protocol, depending on the type of memory in the DIMM.For example, the host can use the protocol of the present disclosure tocommunicate on the same channel (e.g., channel 103-1) with a NVDIMM anda prior protocol to communicate with a DRAM DIMM that are both on thesame memory system 104.

As illustrated in FIG. 1A, a host 102 can be coupled to the memorysystems 104-1 . . . 104-N. In a number of embodiments, each memorysystem 104-1 . . . 104-N can be coupled to host 102 via a channel (e.g.,channels 103-1, . . . , 103-N). In FIG. 1A, memory system 104-1 iscoupled to host 102 via channel 103-1 and memory system 104-N is coupledto host 102 via channel 103-N. Host 102 can be a laptop computer,personal computers, digital camera, digital recording and playbackdevice, mobile telephone, PDA, memory card reader, interface hub, amongother host systems, and can include a memory access device, e.g., aprocessor. One of ordinary skill in the art will appreciate that “aprocessor” can intend one or more processors, such as a parallelprocessing system, a number of coprocessors, etc.

Host 102 includes a host controller 108 to communicate with memorysystems 104-1 . . . 104-N. The host controller 108 can send commands tothe DIMMs 110-1, . . . , 110-X, 110-Y via channels 103-1 . . . 103-N.The host controller 108 can communicate with the DIMMs 110-1, . . . ,110-X, 110-Y and/or the controller 114 on each of the DIMMs 110-1, . . ., 110-X, 110-Y to read, write, and erase data, among other operations. Aphysical host interface can provide an interface for passing control,address, data, and other signals between the memory systems 104-1 . . .104-N and host 102 having compatible receptors for the physical hostinterface. The signals can be communicated between 102 and DIMMs 110-1,. . . , 110-X, 110-Y on a number of buses, such as a data bus and/or anaddress bus, for example, via channels 103-1 . . . 103-N.

The host controller 108 and/or controller 114 on a DIMM can includecontrol circuitry, e.g., hardware, firmware, and/or software. In one ormore embodiments, the host controller 108 and/or controller 114 can bean application specific integrated circuit (ASIC) and/or a fieldprogrammable gate array (FPGA) coupled to a printed circuit boardincluding a physical interface. Also, each DIMM 110-1, . . . , 110-X,110-Y can include buffers 116 of volatile and/or non-volatile memory,registers 107, and background operations 130. Buffer 106 can be used tobuffer data that is used during execution of commands.

The controller 114 can perform background operations 130 on one or moreof the DIMMs 110-1, . . . , 110-X, 110-Y. The controller 114 can performbackground operations on the one or more DIMMs 110-1, . . . , 110-X,110-Y in response to the one or more DIMMs being idle 110-1, . . . ,110-X, 110-Y. In some examples the controller 114 can perform backgroundoperations on the one or more DIMMs 110-1, . . . , 110-X, 110-Y inresponse to the host 102 sending a command to a different memory device.The one or more DIMMs 110-1, . . . , 110-X, 110-Y can stop performingthe background operations 130 in response to the different memory devicecompleting execution of the command.

The different device can use the full bandwidth of the one or morechannels 103-1 . . . 103-N. The one or more DIMMs 110-1, . . . , 110-X,110-Y can be isolated from the host 102 in response to detecting acommand from the host 102 to the different memory device. In someexamples, the background operations 130 can be performed in response tothe one or more DIMMs 110-1, . . . , 110-X, 110-Y being isolated fromthe host 102.

The DIMMs 110-1, . . . , 110-X, 110-Y can provide main memory for thememory system or could be used as additional memory or storagethroughout the memory system. Each DIMM 110-1, . . . , 110-X, 110-Y caninclude one or more arrays of memory cells, e.g., volatile and/ornon-volatile memory cells. The arrays can be flash arrays with a NANDarchitecture, for example. Embodiments are not limited to a particulartype of memory device. For instance, the memory device can include RAM,ROM, DRAM, SDRAM, PCRAM, RRAM, and flash memory, among others.

The embodiment of FIG. 1A can include additional circuitry that is notillustrated so as not to obscure embodiments of the present disclosure.For example, the memory systems 104-1 . . . 104-N can include addresscircuitry to latch address signals provided over I/O connections throughI/O circuitry. Address signals can be received and decoded by a rowdecoder and a column decoder to access the DIMMs 110-1, . . . , 110-X,110-Y. It will be appreciated by those skilled in the art that thenumber of address input connections can depend on the density andarchitecture of the DIMMs 110-1, . . . , 110-X, 110-Y.

FIG. 1B is a block diagram of an apparatus in the form of a dual in-linememory modules (DIMM) 110 in accordance with a number of embodiments ofthe present disclosure. In FIG. 1B, DIMM 110 can include a controller114. Controller 114 can include memory, such as SRAM memory, that can bea buffer 106, a number of registers 107, and background operations 130.DIMM 110 can include a number of memory devices 105-1, . . . , 105-Zcoupled to the controller. Memory devices 105-1, . . . , 105-Z can bevolatile and/or non-volatile memory devices, such as memory devices 221and 224 in FIG. 2, and include non-volatile memory arrays and/orvolatile memory arrays. Memory devices 105-1, . . . , 105-Z can includecontrol circuitry 109 (e.g., hardware, firmware, and/or software) whichcan be used to execute commands on the memory devices 105-1, . . . ,105-Z. The control circuitry 109 can receive commands from controller114. The control circuitry 109 can be configured to execute commands toread and/or write data in the memory devices 105-1, . . . , 105-Z.

FIG. 2 is a block diagram of a computing system 200 including a host 202and a memory system comprising a dual in-line memory module (DIMM) 210with ports in accordance with a number of embodiments of the presentdisclosure. In FIG. 2, host 202 is coupled to DIMM 210 via data buses212-1, . . . , 212-16 and command/address buses 218-1 and 218-2. Host202 can be coupled to DIMM 210 via a number of channels (e.g., channels103-1, . . . , 103-N in FIG. 1A). For example, host 202 is coupled toDIMM 210 via a first channel that includes data buses 212-1, . . . ,212-4 and command/address bus 218 and host 202 is coupled to DIMM 210via a second channel that includes data buses 212-5, . . . , 212-8 andcommand address/bus 2188. Host 202 can send commands on the firstchannel for execution on memory devices 221-1, . . . , 221-8 and memorydevices 224-1, . . . , 224-4 and can send commands on the second channelfor execution on memory devices 221-9, . . . , 221-16 and memory devices224-5, . . . , 224-8. Controller 214 can receive commands from host 202.The commands from host 202 can be sent to register clock driver (RCD)217 via bus 218 and the commands can be sent from RCD 217 to controller214 via bus 219. The controller 214 can receive the commands from RCD217 and store data associated with the commands (e.g., commandinstructions and/or data read from and/or to be written to memorydevices 221 and/or 224 during execution of the commands) in buffer 206.Controller 214 can send a signal to RCD 217 indicating which memorydevice of a pair of memory devices (e.g., memory device 221-1 or 221-2,for example) will execute the command. The signal can be sent from RCD217 to multiplexor 226-1, . . . , 226-8 and cause multiplexor 226-1, . .. , 226-8 to select a memory device from a pair of memory devices andcouple the selected memory device to RCD 217 via bus 225-1 and/or 225-2.For example, if the command is transferring data via an A side port andthe A side port is coupling memory device 221-1 to host 202, while the Bside port is coupling memory device 221-2 to controller 214, the signalcan indicate to multiplexor 226-1 to couple bus 225-1 to memory device221-1. The controller can then send the command to memory device 221-1on bus 225-1 via RCD 217 and memory device 221-1 can execute the commandby transferring data between memory device 221-1 and host 202. Memorydevices 221-1, . . . , 221-16 can send signals, (e.g., commandcompletion signals) on buses 225-1 and 225-2 to RCD 217 and controller214 that indicate memory devices 221-1, . . . , 221-16 have completedexecution of commands and are ready for additional commands. Once acommand has been executed, controller 214 can send another command toRCE 217 for execution and/or a status signal to the host 202 indicatingthat the command received from host 202 has been executed. Controller214 can include non-volatile and/or volatile memory, such as SRAMmemory, that can be a buffer 206, a register 207 used during executionof commands, and/or background operations 230 to be performed by thememory devices 224-1, . . . , 224-8.

DIMM 210 can include a first number of memory devices 221-1, . . . ,221-16. For example, memory devices 221-1, . . . , 221-16 can be DRAMmemory devices, among other types of volatile and/or non-volatilememory. The DRAM memory devices 221-1, . . . , 221-16 can be pairedtogether. For example, DRAM memory devices 221-1 and 221-2 are pairedtogether, coupled to the host via port 222-1 (A Side Port) and buses212-1 and 212-2, and coupled to controller 214 via port 222-2 (B SidePort) and buses 213-1, 213-2, 223-1, and 223-2. DRAM memory devices221-3 and 221-4 are paired together, coupled to the host via port 222-3(A Side Port) and buses 212-3 and 212-4, and coupled to controller 214via port 222-4 (B Side Port) and buses 213-3, 213-4, 223-1, and 223-2.DRAM memory devices 221-5 and 221-6 are paired together, coupled to thehost via port 222-5 (A Side Port) and buses 212-5 and 212-6, and coupledto controller 214 via port 222-6 (B Side Port) and buses 213-5, 213-6,223-1, and 223-2. DRAM memory devices 221-7 and 221-8 are pairedtogether, coupled to the host via port 222-7 (A Side Port) and buses212-7 and 212-8, and coupled to controller 214 via port 222-8 (B SidePort) and buses 213-7, 213-8, 223-1, and 223-2. DRAM memory devices221-9 and 221-10 are paired together, coupled to the host via port 222-9(A Side Port) and buses 212-9 and 212-10, and coupled to controller 214via port 222-10 (B Side Port) and buses 213-9, 213-10, 223-3, and 223-4.DRAM memory devices 221-11 and 221-12 are paired together, coupled tothe host via port 222-11 (A Side Port) and buses 212-11 and 212-12, andcoupled to controller 214 via port 222-12 (B Side Port) and buses213-11, 213-12, 223-3, and 223-4. DRAM memory devices 221-13 and 221-14are paired together, coupled to the host via port 222-13 (A Side Port)and buses 212-13 and 212-14, and coupled to controller 214 via port222-14 (B Side Port) and buses 213-13, 213-14, 223-3, and 223-4. DRAMmemory devices 221-15 and 221-16 are paired together, coupled to thehost via port 222-15 (A Side Port) and buses 212-15 and 212-16, andcoupled to controller 214 via port 222-16 (B Side Port) and buses213-15, 213-16, 223-3, and 223-4.

DIMM 210 can include a second number of memory devices 224-1, . . . ,224-8. For example, memory devices 221-1, . . . , 221-8 can be 3D XPointmemory devices, among other types of volatile and/or non-volatilememory.

Memory system 200 can be configured to execute commands sent from host202 to DIMM 210 by sending command/address information from the hostcontroller 208 on command/address busses 213-1 and 213-2 to the registerclock driver (RCD) 217 and data on data buses 212-1, . . . , 212-16. Thecommands from the host can include address information for memorydevices 221-1, . . . 221-16 where the host is requesting an operation ondata at a particular location in memory devices 221-1, . . . 221-16. Thecommands from the host can include address information for memorydevices 224-1, . . . , 224-8 where the host is requesting an operationon data at particular location in memory devices 224-1, . . . , 224-8,while memory devices 221-1, . . . 221-16 can act as a buffer duringexecution of the commands.

In a number of embodiments, memory devices 221-1, . . . 221-16 can beconfigured as cache. For example, memory devices can be configured ascache for the data stored in memory devices 224-1, . . . , 224-8 and/orother memory devices coupled to the computing system. The DIMM 210 canbe configured to have a portion of memory devices 221-1, . . . 221-16addressable by host 202 and a portion of the memory devices 221-1, . . .221-16 configured as cache.

DIMM 210 includes memory devices that are paired together and one of thepaired memory devices can be selected for coupling to host 202 via an ASide Port and the other of the paired memory device can be selected forcoupling to controller 214 via a B Side Port. For example, memorydevices 221-1, which is paired with memory device 221-2, can be selectedfor coupling to host 202 via port 222-1, while memory device 221-2 canbe selected for coupling to controller 214 via port 222-2. Port 222-1can include a multiplexor to select and couple memory device 221-1 tohost 202 while isolating memory device 221-2 from host 202. Port 222-2can include a multiplexor to select and couple memory device 221-2 tocontroller 214 while isolating memory device 221-1 from controller 214.Host 202 can send command to DIMM 210 for execution on the selected ASide Port memory device (e.g., memory device 221-1). The commands can beexecuted by transferring data between host 202 and memory device 221-1via port 222-1 on buses 212-1 and/or 212-2. DIMM 210 can also executecommands for execution on the selected B Side Port memory device (e.g.,memory device 221-2). The commands can be executed by transferring databetween memory device 221-2 and other memory devices via port 222-1 andcontroller 214 on buses 212-1, 212-2, 223-1, and/or 223-2. Commandsexecuted using the B Side Port can transfer data between memory devices221-1, . . . , 221-16 and/or between memory devices 221-1, . . . ,221-16 and memory devices 224-1, . . . , 224-8. Ports 222-1, . . . ,22-16 can be external to memory devices 221-1, . . . , 221-16 asillustrated in FIG. 2.

In a number of embodiments, commands that transfer data via the A SidePorts can be executed while commands that transfer data via the B SidePorts. The data that is stored in pairs memory devices can be arbitratedand reconciled by the controller. Memory devices that have executedcommands where data was transferred to and/or from one of the memorydevices on the A Side Port and to and/or from the other paired memorydevice on the B Side Port can have the data on the pair of memory devicereconciled by transferring data between the pair of memory devicesand/or between the pair of memory devices and memory devices 224-1, . .. , 224-8. For example, after A Side Port and B Side Port transfers haveoccurred on a pair of memory devices and DIMM 210 is idle, controller214 can send commands to reconcile the data stored on the pair of memorydevices so that the same data is stored on each of the memory devices bytransferring data between the pair of memory devices and/or between thepair of memory devices and memory devices 224-1, . . . , 224-8.

In a number of embodiments, commands can be received from host 202and/or generated by controller 214 to transfer data between memorydevices 224-1, . . . , 224-8. Data can be transferred between memorydevices 224-1, . . . , 224-8 via controller 214 using buffer 206 and/orregisters 207.

In a number of embodiments, the controller 214 can be configured toperform a background operation 230 on one or more memory devices 224-1,. . . , 224-8. The controller 214 can perform the background operation230 on the one or more memory devices 224-1, . . . , 224-8 in responseto the one or more memory devices 224-1, . . . , 224-8 being idle. Theone or more memory devices 224-1, . . . , 224-8 can be idle when the oneor more memory devices 224-1, . . . , 224-8 are not executing a commandfrom the host 202.

In some examples, the controller 214 can perform the backgroundoperation 230 on the one or more memory devices 224-1, . . . , 224-8 inresponse to the host 202 sending non-target commands and/or whennon-target commands are being executed. For example, a non-targetcommand can be a command to one or more memory devices 221-1, . . . ,221-16 that are not the one or more memory devices 224-1, . . . , 224-8.The command can be directed to a memory device 221-1 to perform a readoperation and the memory device 224-1 can perform a background operation230 in response to the host 202 sending the command to the memory device221-1, for example.

In a number of embodiments, the one or more memory devices 224-1, . . ., 224-8 can stop performing the background operation 230 in response tothe one or more memory devices 221-1, . . . , 221-16 completingexecution of the command.

The one or more memory devices 224-1, . . . , 224-8 can be isolated fromthe host 202 in response to detecting a command from the host 202 to theone or more memory devices 221-1, . . . , 221-16. One or moremultiplexors 226-1, . . . , 226-8 can isolate the one or more memorydevices 224-1, . . . , 224-8 from the host 202. In some examples, thebackground operation 230 can be performed in response to the one or morememory devices 224-1, . . . , 224-8 being isolated from the host 202.For example, memory device 224-1 can be isolated from the host 202 bymultiplexor 226-1 in response to detecting a command from the host 202directed to the memory device 221-1.

In a number of embodiments, the one or more memory devices 224-1, . . ., 224-8 can receive a different command from the host 202. The one ormore memory devices 224-1, . . . , 224-8 can delay execution of thedifferent command until the command to the one or more memory devices221-1, . . . , 221-15 is complete.

FIG. 3 is a block diagram of a computing system 300 including a host 302and a memory system comprising a dual in-line memory module (DIMM) 310with a ready/busy bus in accordance with a number of embodiments of thepresent disclosure. In FIG. 3, host 302 is coupled to DIMM 310 via databuses 312-1, . . . , 312-16, command/address bus 318, and ready/busy bus327. Host 302 can be coupled to DIMM 310 via a number of channels (e.g.,channels 103-1, . . . , 103-N in FIG. 1A). For example, host 302 iscoupled to DIMM 310 via a first channel that includes data buses 312-1,. . . , 312-4, command/address bus 318, and ready/busy bus 327; and host302 is coupled to DIMM 310 via a second channel that includes data buses312-5, . . . , 312-8, command address/bus 318, and ready/busy bus 327.

DIMM 310 can include a first number of memory devices 321-1, . . . ,321-8. For example, memory devices 321-1, . . . , 321-16 can be DRAMmemory devices, among other types of volatile and/or non-volatilememory. DIMM 310 can include a second number of memory devices 324-1, .. . , 324-8. For example, memory devices 321-1, . . . , 321-8 can be 3DXPoint memory devices, among other types of volatile and/or non-volatilememory.

Controller 314 can send a ready/busy signal to host 302 on theready/busy bus 327. The ready/busy signal can indicate to host 302whether or not the controller is ready to receive commands from host302. For example, if DIMM 310 is busy executing commands, such astransferring data between memory devices 321-1, . . . , 321-4 and memorydevices 324-1, . . . , 324-4, for example, the DIMM and is not ready toreceive commands, so a ready/busy signal can be sent on ready/busy bus327 to host 302 that indicates DIMM 310 is not ready to receivecommands. Once DIMM 310 is no longer busy executing commands DIMM 310can send a ready/busy signal on ready/busy bus 327 to host 302indicating DIMM 310 is ready to receive commands from host 302. Host 302can send commands to DIMM 310 in response to receiving the ready/busysignal.

Controller 314 can receive commands from host 302. The commands fromhost 302 can be sent to register clock driver (RCD) 317 via bus 318 andthe commands can be sent from RCD 317 to controller 314 via bus 319.Controller 314 can receive the commands from RCD 317 and store dataassociated with the commands (e.g., command instructions and/or dataread from and/or to be written to memory devices 321 and/or 324 duringexecution of the commands) in buffer 306. The controller can send thecommands to memory devices 321-1, . . . , 321-8 on bus 325-1 and/or325-2 via RCD 317 and memory devices 321-1, . . . , 321-8 can executethe commands by transferring data between memory devices 321-1, . . . ,321-8 and host 302 and/or memory devices 321-1, . . . , 321-8 and memorydevice 324-1, . . . , 324-8. Memory devices 321-1, . . . , 321-8 cansend signals on buses 325-1 and 325-2 to RCD 317 and controller 314 thatindicate memory devices 321-1, . . . , 321-8 have completed execution ofcommands and are ready for additional commands. Once a command has beenexecuted, controller 314 can send a status signal to the host 302indicating that the command received from host 302 has been executed.Controller 314 can include non-volatile and/or volatile memory, such asSRAM memory, that can be a buffer 306, a register 307 used duringexecution of commands, and background operations 330 to be performed bythe memory devices 324-1, . . . , 324-8.

Memory system 300 can be configured to execute commands sent from host302 to DIMM 310 by sending command/address information from the hostcontroller 308 on command/address bus 318 to the register clock driver(RCD) 317 and data on data buses 312-1, . . . , 312-8. The commands fromthe host can include address information for memory devices 321-1, . . .321-8 where the host is requesting an operation on data at particularlocation in memory devices 321-1, . . . 321-16. The commands from thehost can include address information for memory devices 324-1, . . . ,324-4 where the host is requesting an operation on data at particularlocation in memory devices 324-1, . . . , 324-4, while memory devices321-5, . . . 321-8 can act as a buffer during execution of the commands.

In a number of embodiments, memory devices 321-1, . . . 321-8 can beconfigured as cache. For example, memory devices can be configured ascache for the data stored in memory devices 324-1, . . . , 324-8 and/orother memory devices coupled to the computing system. The DIMM 310 canbe configured to have a portion of memory devices 321-1, . . . 321-8addressable by host 302 and a portion of the memory devices 321-1, . . .321-8 configured as cache.

In a number of embodiments, commands can be received from host 302and/or generated by controller 314 to transfer data between memorydevices 324-1, . . . , 324-8. Data can be transferred between memorydevices 324-1, . . . , 324-8 via controller 314 using buffer 306 and/orregisters 307.

FIG. 4 is a block diagram of a computing system 400 including a host 402and a memory system comprising a dual in-line memory module (DIMM) 410with a first and second controller in accordance with a number ofembodiments of the present disclosure. In FIG. 4, host 402 is coupled toDIMM 210 via data buses 412-1, . . . , 412-8 and command/address buses418-1 and 418-2. Host 402 can be coupled to DIMM 410 via a number ofchannels (e.g., channels 103-1, . . . , 103-N in FIG. 1A). For example,host 402 is coupled to DIMM 410 via a first channel that includes databuses 412-1, . . . , 412-4 and command/address bus 418-1 and host 402 iscoupled to DIMM 410 via a second channel that includes data buses 412-5,. . . , 412-9 and command address/bus 418-2. Host 402 can send commandson the first channel for execution on memory devices 421-1, . . . ,421-8 and memory devices 424-1, . . . , 424-4 and can send commands onthe second channel for execution on memory devices 421-9, . . . , 421-16and memory devices 424-5, . . . , 424-8. Controller 414-1 can receivecommands from host 402 on channel 1 and controller 414-2 can receivecommands from 402 on channel 2. The commands from host 402 can be sentto register clock driver (RCD) 417 via buses 418-1 and/or 418-2 and thecommands can be sent from RCD 417 to controller 414-1 via bus 419-1 andcontroller 414-2 via bus 419-2.

DIMM 410 can include controller 414-1 and 414-2. Controller 414-1 can becoupled to and send signals to control operation of memory devices421-1, . . . , 421-8 and memory devices 424-1, . . . , 424-4. Controller414-2 can be coupled to and send signals to control operation of memorydevices 421-9, . . . , 421-16 and memory devices 424-8, . . . , 424-8.DIMM 410 with controllers 414-1 and 414-2 can allow memory devices421-1, . . . , 421-8 and memory devices 424-1, . . . , 424-4 tooperation independently from memory devices 421-9, . . . , 421-16 andmemory devices 424-8, . . . , 424-8. Controller 414-1 is coupled tocontroller 414-2 can data can be transferred between controller 414-1and 414-2. Therefore controller 414-1 can operate memory devices 421-1,. . . , 421-8 and memory devices 424-1, . . . , 424-4 independently fromother memory device and also transfer data from memory devices 421-1, .. . , 421-8 and memory devices 424-1, . . . , 424-4 to other memorydevices, such as memory devices 421-9, . . . , 421-16 and memory devices424-8, . . . , 424-8.

The controller 414 can receive the commands from RCD 417 and store dataassociated with the commands (e.g., command instructions and/or dataread from and/or to be written to memory devices 421 and/or 424 duringexecution of the commands) in buffer 406. Controller 414 can send asignal to RCD 417 indicating which memory device of a pair of memorydevices (e.g., memory device 421-1 or 421-2, for example) will executethe command. The signal can be sent from RCD 217 to multiplexor 426-1, .. . , 426-8 and cause multiplexor 426-1, . . . , 426-8 to select amemory device from a pair of memory devices and couple the selectedmemory device to RCD 417 via bus 425-1 and/or 425-2. For example, if thecommand is transferring data via an A side port and the A side port iscoupling memory device 421-1 to host 402, while the B side port iscoupling memory device 421-2 to controller 414, the signal can indicateto multiplexor 426-1 to couple bus 425-1 to memory device 421-1. Thecontroller can then send the command to memory device 421-1 on bus 425-1via RCD 417 and memory device 421-1 can execute the command bytransferring data between memory device 421-1 and host 402. Memorydevices 421-1, . . . , 421-16 can send signals on buses 425-1 and 425-2to RCD 417 and controller 414 that indicate memory devices 421-1, . . ., 421-16 have completed execution of commands and are ready foradditional commands. Once a command has been executed, controller 414can send a status signal to the host 402 indicating that the commandreceived from host 402 has been executed. Controllers 414-1 and 414-2can include non-volatile and/or volatile memory, such as SRAM memory,that can be a buffer 406, a register 407 used during execution ofcommands, and/or background operations 430 to be performed on the memorydevices 424-1, . . . , 424-8.

DIMM 410 can include a first number of memory devices 421-1, . . .421-16. For example, memory devices 421-1, . . . 421-16 can be DRAMmemory devices, among other types of volatile and/or non-volatilememory. The DRAM memory devices 421-1, . . . 421-16 can be pairedtogether. For example, DRAM memory devices 421-1 and 421-2 are pairedtogether, coupled to the host via ports 422-1 and 422-2 (A Side Ports)and bus 412-1, and coupled to controller 414-1 via ports 422-17 and422-18 (B Side Ports) and buses 413-1 and 423-1. DRAM memory devices421-3 and 421-4 are paired together, coupled to the host via ports 422-3and 422-3 (A Side Ports) and bus 412-2, and coupled to controller 414-1via ports 422-19 and 422-20 (B Side Ports) and buses 413-2 and 423-1.DRAM memory devices 421-5 and 421-6 are paired together, coupled to thehost via ports 422-5 and 422-6 (A Side Ports) and bus 412-3, and coupledto controller 414-1 via ports 422-21 and 422-22 (B Side Ports) and buses413-3 and 423-1. DRAM memory devices 421-7 and 421-8 are pairedtogether, coupled to the host via ports 422-7 and 422-8 (A Side Ports)and buses 412-4, and coupled to controller 414-1 via ports 422-23 and422-24 (B Side Ports) and buses 413-4 and 423-1. DRAM memory devices421-9 and 421-10 are paired together, coupled to the host via ports422-9 and 422-10 (A Side Ports) and bus 412-5, and coupled to controller414-2 via ports 422-25 and 42-26 (B Side Ports) and buses 413-5 and423-2. DRAM memory devices 421-11 and 421-12 are paired together,coupled to the host via ports 422-11 and 422-12 (A Side Ports) and bus412-6, and coupled to controller 414-2 via ports 422-27 and 422-28 (BSide Ports) and buses 413-6 and 423-2. DRAM memory devices 421-13 and421-14 are paired together, coupled to the host via ports 422-13 and422-14 (A Side Ports) and bus 412-7, and coupled to controller 414-2 viaports 422-29 and 422-30 (B Side Ports) and buses 413-7 and 423-2. DRAMmemory devices 421-15 and 421-16 are paired together, coupled to thehost via ports 422-15 and 422-16 (A Side Ports) and bus 412-8, andcoupled to controller 414-2 via ports 422-31 and 422-32 (B Side Ports)and buses 413-8 and 423-2.

DIMM 410 can include a second number of memory devices 424-1, . . .424-8. For example, memory devices 421-1, . . . 421-8 can be 3D XPointmemory devices, among other types of volatile and/or non-volatilememory.

Memory system 400 can be configured to execute commands sent from host402 to DIMM 210 by sending command/address information from the hostcontroller 408 on command/address busses 413-1 and 413-2 to the registerclock driver (RCD) 217 and data on data buses 412-1, . . . , 412-16. Thecommands from the host can include address information for memorydevices 421-1, . . . 421-16 where the host is requesting an operation ondata at particular location in memory devices 421-1, . . . 421-16. Thecommands from the host can include address information for memorydevices 424-1, . . . , 424-8 where the host is requesting an operationon data at particular location in memory devices 424-1, . . . , 424-8,while memory devices 421-1, . . . 421-16 can act as a buffer duringexecution of the commands.

In a number of embodiments, memory devices 421-1, . . . 421-16 can beconfigured as cache. For example, memory devices can be configured ascache for the data stored in memory devices 424-1, . . . , 424-8 and/orother memory devices coupled to the computing system. The DIMM 410 canbe configured to have a portion of memory devices 421-1, . . . 421-16addressable by host 402 and a portion of the memory devices 421-1, . . .421-16 configured as cache.

DIMM 410 includes memory devices that are paired together and one of thepaired memory devices can be selected for coupling to host 402 via an ASide Port and the other of the paired memory device can be selected forcoupling to controller 414 via a B Side Port. For example, memorydevices 421-1, which is paired with memory device 421-2, can be selectedfor coupling to host 402 via port 422-1, while memory device 421-2 canbe selected for coupling to controller 414-1 via port 422-2. Port 422-1can include a multiplexor to select and couple memory device 421-1 tohost 402 while isolating memory device 421-2 from host 402. Port 422-2can include a multiplexor to select and couple memory device 421-2 tocontroller 414-1 while isolating memory device 421-1 from controller414. Host 402 can send command to DIMM 210 for execution on the selectedA Side Port memory device (e.g., memory device 421-1). The commands canbe executed by transferring data between host 402 and memory device421-1 via port 422-1 on buses 412-1 and/or 412-2. DIMM 210 can alsoexecute commands for execution on the selected B Side Port memory device(e.g., memory device 421-2). The commands can be executed bytransferring data between memory device 421-2 and other memory devicesvia port 422-1 and controller 414-1 on buses 412-1, 412-2, 423-1, and/or423-2. Commands executed using the B Side Port can transfer data betweenmemory devices 421-1, . . . , 421-16 and/or between memory devices421-1, . . . , 421-16 and memory devices 424-1, . . . , 424-8. Ports422-1, . . . , 422-32 can be external to memory devices 421-1, . . . ,421-16 as illustrated in FIG. 4.

In a number of embodiments, commands that transfer data via the A SidePorts can be executed while commands that transfer data via the B SidePorts. The data that is stored in pairs memory devices can be arbitratedand reconciled by the controller. Memory devices that have executedcommands where data was transferred to and/or from one of the memorydevices on the A Side Port and to and/or from the other paired memorydevice on the B Side Port can have the data on the pair of memory devicereconciled by transferring data between the pair of memory devicesand/or between the pair of memory devices and memory devices 424-1, . .. , 424-8. For example, after A Side Port and B Side Port transfers haveoccurred on a pair of memory devices and DIMM 210 is idle, controllers414-1 and 414-2 can send commands to reconcile the data stored on thepair of memory devices so that the same data is stored on each of thememory devices by transferring data between the pair of memory devicesand/or between the pair of memory devices and memory devices 424-1, . .. , 424-8.

In a number of embodiments, commands can be received from host 402and/or generated by controllers 414-1 and 414-2 to transfer data betweenmemory devices 424-1, . . . , 424-8. Data can be transferred betweenmemory devices 424-1, . . . , 424-8 via controllers 414-1 and 414-2using buffer 406 and/or registers 407.

In a number of embodiments, the controller 414-1 can be configured toperform background operations 430 on one or more memory devices 424-1, .. . , 424-4. The controller 414-1 can perform the background operations430 on the one or more memory devices 424-1, . . . , 424-4 in responseto the one or more memory devices 424-1, . . . , 424-4 being idle. Insome examples, the controller 414-1 can perform the backgroundoperations 430 on the one or more memory devices 424-1, . . . , 424-4 inresponse to the host 402 sending a command to one or more memory devices421-1, . . . , 421-8. The command can be to a memory device 421-1 torefresh the memory device 421-1 and the memory device 424-1 can performa background operation 430 in response to the host 402 sending thecommand to the memory device 421-1. In some examples, the one or morememory devices 424-1, . . . , 424-4 can stop performing the backgroundoperations 430 in response to the one or more memory devices 421-1, . .. , 421-8 completing execution of the command.

The one or more memory devices 424-1, . . . , 424-4 can be isolated fromthe host 402 in response to detecting a command from the host 402directed to the one or more memory devices 421-1, . . . , 421-8. One ormore multiplexors 426-1, . . . , 426-4 can isolate the one or morememory devices 424-1, . . . , 424-4 from the host 402. In some examples,the background operation 430 can be performed in response to the one ormore memory devices 424-1, . . . , 424-4 being isolated from the host402. For example, memory device 424-1 can be isolated from the host 402by multiplexor 426-1 in response to detecting a command from the host402 directed to the memory device 421-1.

In a number of embodiments, the one or more memory devices 424-1, . . ., 424-4 can receive a different command from the host 402. The one ormore memory devices 424-1, . . . , 424-4 can delay execution of thedifferent command until the command to the one or more memory devices421-1, . . . , 421-8 is complete.

In a number of embodiments, the controller 414-2 can be configured toperform background operations 430 on one or more memory devices 424-5, .. . , 424-8. The controller 414-2 can perform the background operations430 on the one or more memory devices 424-5, . . . , 424-8 in responseto the one or more memory devices 424-5, . . . , 424-8 being idle. Insome examples, the controller 414-2 can perform the backgroundoperations 430 on the one or more memory devices 424-5, . . . , 424-8 inresponse to the host 402 sending a command to one or more memory devices421-9, . . . , 421-16. The command can be directed to a memory device421-9 to perform a read operation and the memory device 424-5 canperform a background operation 430 in response to the host 402 sendingthe command to the memory device 421-9. In some examples, the one ormore memory devices 424-5, . . . , 424-8 can stop performing thebackground operations 430 in response to the one or more memory devices421-9, . . . , 421-16 completing execution of the command.

The one or more memory devices 424-5, . . . , 424-8 can be isolated fromthe host 402 in response to detecting a command from the host 402 to theone or more memory devices 421-9, . . . , 421-16. One or moremultiplexors 426-5, . . . , 426-8 can isolate the one or more memorydevices 424-5, . . . , 424-8 from the host 402. In some examples, thebackground operation 430 can be performed in response to the one or morememory devices 424-5, . . . , 424-8 being isolated from the host 402.For example, memory device 424-5 can be isolated from the host 402 bymultiplexor 426-5 in response to detecting a command from the host 402to the memory device 421-9.

In a number of embodiments, the one or more memory devices 424-5, . . ., 424-8 can receive a different command from the host 402. The one ormore memory devices 424-5, . . . , 424-8 can delay execution of thedifferent command until the command to the one or more memory devices421-9, . . . , 421-16 is complete.

FIG. 5 is a block diagram of a computing system 500 including a host 502and a memory system comprising a dual in-line memory module (DIMM) 510with a first and second controller and a first and second ready/busy busin accordance with a number of embodiments of the present disclosure. InFIG. 5, host 502 is coupled to DIMM 510 via data buses 512-1, . . . ,512-16, command/address buses 518-1 and 518-2, and ready/busy buses527-1 and 527-2. Host 502 can be coupled to DIMM 510 via a number ofchannels (e.g., channels 103-1, . . . , 103-N in FIG. 1A). For example,host 502 is coupled to DIMM 510 via a first channel that includes databuses 512-1, . . . , 512-4, command/address bus 518-1, and ready/busybus 527-1; and host 502 is coupled to DIMM 510 via a second channel thatincludes data buses 512-5, . . . , 512-8, command address/bus 518-2, andready/busy bus 527-2. Controller 514-1 can receive commands from host502 on channel 1 and controller 514-2 can receive commands from host 502on channel 2. The commands from host 502 can be sent to register clockdriver (RCD) 517 via buses 518-1 and/or 518-2 and the commands can besent from RCD 517 to controller 514-1 via bus 519-1 and controller 514-2via bus 519-2.

DIMM 510 can include controller 514-1 and 514-2. Controller 514-1 can becoupled to and send signals to control operation of memory devices521-1, . . . , 521-4 and memory devices 424-1, . . . , 424-4. Controller514-2 can be coupled to and send signals to control operation of memorydevices 521-5, . . . , 521-8 and memory devices 524-5, . . . , 524-8.DIMM 510 with controllers 514-1 and 514-2 can allow memory devices521-1, . . . , 521-4 and memory devices 524-1, . . . , 524-4 tooperation independently from memory devices 521-5, . . . , 521-8 andmemory devices 524-5, . . . , 524-8. Controller 514-1 is coupled tocontroller 514-2 and data can be transferred between controller 514-1and 514-2. Therefore controller 514-1 can operate memory devices 521-1,. . . , 521-4 and memory devices 524-1, . . . , 524-4 independently fromother memory device and also transfer data from memory devices 521-1, .. . , 521-4 and memory devices 524-1, . . . , 524-4 to other memorydevices, such as memory devices 521-5, . . . , 451-8 and memory devices524-5, . . . , 524-8.

DIMM 510 can include a first number of memory devices 521-1, . . . ,521-8. For example, memory devices 521-1, . . . , 521-8 can be DRAMmemory devices, among other types of volatile and/or non-volatilememory. DIMM 510 can include a second number of memory devices 524-1, .. . , 524-8. For example, memory devices 521-1, . . . , 521-8 can be 3DXPoint memory devices, among other types of volatile and/or non-volatilememory.

Controllers 514-1 and 514-2 can send a ready/busy signal to host 502 onthe ready/busy buses 527-1 and 524-2, respectively. The ready/busysignal can indicate to host 502 whether or not the controller 514-1and/or 514-2 is ready to receive commands from host 502. For example, ifcontroller 514-1 on DIMM 510 is busy executing commands, such astransferring data between memory devices 521-1, . . . , 521-4 and memorydevices 524-1, . . . , 524-4 the controller 514-1 is not ready toreceive commands on channel 1, but controller 514-2 could receivecommands on channel 2. A ready/busy signal can be sent by controller514-1 on ready/busy bus 527-1 to host 502 that indicates controller514-1 is not ready to receive commands on channel 1 and a ready/busysignal can be sent by controller 514-2 on ready/busy bus 527-2 to hostindicating controller 514-2 is ready to receive command from host 502 onchannel 2. Host 502 can send commands on the second channel tocontroller 514-2 for execution on memory device 521-5, . . . , 521-8and/or memory devices 524-5, . . . , 524-8. Once controller 514-1 is nolonger busy executing commands, such as commands that transfer data onmemory device associated with channel 1, controller 514-1 can send aready/busy signal on ready/busy bus 527-1 to host 502 indicatingcontroller 514-1 is ready to receive commands from host 502 on channel1. Host 502 can send commands to controller 514-1 on channel 1 inresponse to receiving the ready/busy signal.

Controllers 514-1 and 514-2 can receive commands from host 502. Thecommands from host 502 can be sent to register clock driver (RCD) 517via buses 518-1 and/or 518-2 and the commands can be sent from RCD 517to controllers 514-1 and 514-2 via buses 519-1 and/or 519-2,respectively. Controllers 514-1 and 514-2 can receive the commands fromRCD 517 and store data associated with the commands (e.g., commandinstructions and/or data read from and/or to be written to memorydevices 521 and/or 524 during execution of the commands) in buffer 506.Controllers 514-1 and 514-2 can send the commands to memory devices521-1, . . . , 521-8 on bus 525-1 and/or 525-2 via RCD 517 and memorydevices 521-1, . . . , 521-8 can execute the commands by transferringdata between memory devices 521-1, . . . , 521-8 and host 502 and/ormemory devices 521-1, . . . , 521-8 and memory device 524-1, . . . ,524-8. Memory devices 521-1, . . . , 521-8 can send signals on buses525-1 and 525-2 to RCD 517 and controllers 514-1 and 514-2 that indicatememory devices 521-1, . . . , 521-8 have completed execution of commandsand are ready for additional commands. Once a command has been executed,controllers 514-1 and 514-2 can send a status signal to the host 502indicating that the command received from host 502 has been executed.Controllers 514-1 and 514-2 can include non-volatile and/or volatilememory, such as SRAM memory, that can be a buffer 506, a register 507used during execution of commands, and/or background operations 530 tobe performed on the memory devices 524-1, . . . , 524-8.

Memory system 500 can be configured to execute commands sent from host502 to DIMM 510 by sending command/address information from the hostcontroller 508 on command/address bus 518 to the register clock driver(RCD) 517 and data on data buses 512-1, . . . , 512-8. The commands fromthe host can include address information for memory devices 521-1, . . .521-8 where the host is requesting an operation on data at particularlocation in memory devices 521-1, . . . 521-16. The commands from thehost can include address information for memory devices 524-1, . . . ,524-4 where the host is requesting an operation on data at particularlocation in memory devices 524-1, . . . , 524-4, while memory devices521-5, . . . 521-8 can act as a buffer during execution of the commands.

In a number of embodiments, memory devices 521-1, . . . 521-8 can beconfigured as cache. For example, memory devices can be configured ascache for the data stored in memory devices 524-1, . . . , 524-8 and/orother memory devices coupled to the computing system. The DIMM 510 canbe configured to have a portion of memory devices 521-1, . . . 521-8addressable by host 502 and a portion of the memory devices 521-1, . . .521-8 configured as cache.

In a number of embodiments, commands can be received from host 502and/or generated by controllers 514-1 and 514-2 to transfer data betweenmemory devices 524-1, . . . , 524-8. Data can be transferred betweenmemory devices 524-1, . . . , 524-8 via controllers 514-1 and 514-2using buffers 506 and/or registers 507.

The controllers 514-1 and 514-2 can be configured to perform backgroundoperations 530 on the memory devices 524-1, . . . , 524-8. For example,the controller 514-1 can perform a background operation 530 on thememory device 524-1 in response to the controller 514-1 sending aready/busy signal to the host 502 indicating the controller 514-1 is notready to receive commands on channel 1.

In a number of embodiments, the controllers 514-1 and 514-2 can beconfigured to stop performing background operations 630 on the memorydevices 524-1, . . . , 524-8. For example, the controller 514-1 can stopperforming a background operation 530 on the memory device 524-1 inresponse to the controller 514-1 sending a ready/busy signal to the host502 indicating the controller 514-1 is ready to receive commands onchannel 1. FIG. 6 is a block diagram of a controller includingbackground operations and a time calculator in accordance with a numberof embodiments.

As discussed, above, the controller 614 can perform backgroundoperations 630 on memory devices (e.g., memory devices 524-1, . . . ,524-8 in FIG. 5). The background operations 630 can include clearingdata 634. For example, the memory devices can be configured to clearunused data as a background operation 630. A memory device can clearunused data in response to the memory device being idle and/or inresponse to a host (e.g., host 502 in FIG. 5) sending a command to adifferent memory device (e.g., memory devices 521-1, . . . , 521-16 inFIG. 5).

The background operations 630 can include performing garbage collection636 on memory devices (e.g., memory devices 524-1, . . . , 524-8 in FIG.5). Garbage collection can include moving and/or erasing data to freeportions of memory devices for future use. For example, the memorydevices can be configured to perform garbage collection 636 in responseto the memory device being idle and/or in response to the host (e.g.,host 502 in FIG. 5) sending a command to a different memory device(e.g., memory devices 521-1, . . . , 521-16 in FIG. 5).

In a number of embodiments, the background operations 630 can includeadjusting threshold voltages 638 of the memory devices (e.g., memorydevices 524-1, . . . , 524-8 in FIG. 5). For example, the memory devicescan be configured to adjust threshold voltages 638 in response to thememory device being idle and/or in response to the host (e.g., host 502in FIG. 5) sending a command to a different memory device (e.g., memorydevices 521-1, . . . , 521-16 in FIG. 5).

The background operations 630 can also include performing a reconcileoperation on the memory devices (e.g., 521-1, . . . , 521-16 in FIG. 5).For example, the memory device (e.g., memory device 521-1 in FIG. 5) canreconcile the data stored on it to match the data stored on its pair(e.g., memory device 521-2 in FIG. 5) by transferring data between thememory device and another memory device (e.g., memory device 524-1 inFIG. 5). The reconcile operation 639 can be done in response to thememory device being idle and/or the host (e.g., host 502 in FIG. 5)sending a command to the pair, for example.

The background operations 630 can be clearing data 634, performinggarbage collection 636, adjusting threshold voltages 638, andreconciling data, but the background operations 630 are not limited tothese operations.

In a number of embodiments, the controller 614 can include a timecalculator 632. As discussed above, the background operations 630 can beperformed on a memory device (e.g., memory devices 524-1, . . . , 524-8in FIG. 5) in response to the host (e.g., host 502 in FIG. 5) sending acommand to a different memory device (e.g., memory devices 521-1, . . ., 521-16). The time calculator 632 can be used to calculate the periodof time it will take for the different memory device to execute thecommand. The memory device can choose which background operations toperform and/or what number of background operations to perform based onthe period of time it will take for the different memory device toexecute the command.

FIG. 7 is a flow diagram illustrating an example of performing abackground operation on a memory device in accordance with a number ofembodiments of the present disclosure. The process described in FIG. 7can be performed by, for example, a memory device such as memory device524-1 shown in FIG. 5.

At block 742, the method 740 can include detecting a command sent from ahost (e.g., host 502 in FIG. 5) to at least one memory device on a dualin-line memory module (DIMM) having a plurality of memory devices. Insome examples, a controller (e.g., controller 514 in FIG. 5) and/or amemory device (e.g., memory device 524-1, . . . , 524-8) can detect thecommand.

At block 744, the method 740 can further include identifying an idlestate of a first memory device (e.g., memory device 524-1 in FIG. 5) ofthe plurality of memory devices. In some examples, the first memorydevice can be idle when the first memory device has no commands toperform.

At block 746, the method 740 can further include determining that thecommand is directed to a second memory device (e.g., memory device 521-1in FIG. 5) of the plurality of memory devices.

At block 748, the method 740 can further include performing a backgroundoperation on the first memory device in response to the identified idlestate of the first memory device and determining that the command isdirected to the second memory device

Although specific embodiments have been illustrated and describedherein, those of ordinary skill in the art will appreciate that anarrangement calculated to achieve the same results can be substitutedfor the specific embodiments shown. This disclosure is intended to coveradaptations or variations of various embodiments of the presentdisclosure. It is to be understood that the above description has beenmade in an illustrative fashion, and not a restrictive one. Combinationof the above embodiments, and other embodiments not specificallydescribed herein will be apparent to those of skill in the art uponreviewing the above description. The scope of the various embodiments ofthe present disclosure includes other applications in which the abovestructures and methods are used. Therefore, the scope of variousembodiments of the present disclosure should be determined withreference to the appended claims, along with the full range ofequivalents to which such claims are entitled.

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described herein can be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations.

Also, as used herein, including in the claims, “or” as used in a list ofitems (for example, a list of items prefaced by a phrase such as “atleast one of” or “one or more of”) indicates an inclusive list suchthat, for example, a list of at least one of A, B, or C means A or B orC or AB or AC or BC or ABC (i.e., A and B and C). For the avoidance ofdoubt, a list of at least one of A, B, or C, or any combination thereofis likewise an inclusive list. Also, as used herein, the phrase “basedon” shall not be construed as a reference to a closed set of conditions.For example, an exemplary step that is described as “based on conditionA” may be based on both a condition A and a condition B withoutdeparting from the scope of the present disclosure. In other words, asused herein, the phrase “based on” shall be construed in the same manneras the phrase “based at least in part on.”

In the foregoing Detailed Description, various features are groupedtogether in a single embodiment for the purpose of streamlining thedisclosure. This method of disclosure is not to be interpreted asreflecting an intention that the disclosed embodiments of the presentdisclosure have to use more features than are expressly recited in eachclaim. Rather, as the following claims reflect, inventive subject matterlies in less than all features of a single disclosed embodiment. Thus,the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separateembodiment.

What is claimed is:
 1. An apparatus, comprising: a memory device; and acontroller coupled to the memory device via a register clock driver,wherein the controller is configured to: send a ready/busy signal to ahost via a ready/busy signal bus; and send a command to the memorydevice to perform a background operation in response to sending theready/busy signal to the host; and wherein the memory device isconfigured to: perform a background operation in response to receivingthe command from the controller.
 2. The apparatus of claim 1, whereinthe ready/busy signal indicates that the controller is busy.
 3. Theapparatus of claim 2, wherein the controller is busy in response to adual in-line memory module (DIMM) executing a command.
 4. The apparatusof claim 3, wherein the DIMM includes the memory device and a differentmemory device.
 5. The apparatus of claim 4, wherein the DIMM executingthe command includes the memory device transferring data to thedifferent memory device.
 6. The apparatus of claim 3, wherein the DIMMsends a second ready/busy signal to the host in response to completingthe execution of the command.
 7. The apparatus of claim 6, wherein theDIMM receives a command from the host in response to sending the secondready/busy signal.
 8. The apparatus of claim 1, wherein the backgroundoperation includes performing garbage collection on the memory device.9. The apparatus of claim 1, wherein the background operation includesadjusting threshold voltages.
 10. The apparatus of claim 1, wherein thebackground operation includes performing a reconcile operation on thememory device.
 11. The apparatus of claim 10, wherein the reconcileoperation includes transferring data between the memory device and adifferent memory device.
 12. A system, comprising: a host; and a memorydevice and a controller on a dual in-line memory module (DIMM), whereinthe controller is coupled to the host via a ready/busy signal bus andthe memory device is coupled to the controller via a register clockdriver; wherein the controller is configured to: send a ready/busysignal to the host; and send a command to the memory device on the DIMMin response to sending the ready/busy signal to the host; and whereinthe memory device is configured to: execute a background operation inresponse to receiving the command from the controller.
 13. The system ofclaim 12, wherein the controller is configured to send a differentready/busy signal via the ready/busy signal bus to the host in responseto the background operation being executed.
 14. The system of claim 13,wherein the host is configured to send a command to the controller via aregister clock driver (RCD), a first bus, and a second bus in responseto receiving the different ready/busy signal.
 15. The system of claim14, wherein the controller is configured to send a different command tothe memory device via the RCD in response to receiving the command fromthe host.
 16. A method, comprising: sending a first ready/busy signal toa host from a controller on a dual in-line memory module (DIMM) via aready/busy signal bus; executing, via the controller, a backgroundoperation on a memory device on the DIMM in response to sending theready/busy signal to the host; sending a second ready/busy signal to thehost from the controller via the ready/busy signal bus in response toexecuting the background operation; receiving a command from the host atthe controller in response to the controller sending the secondready/busy signal to the host; and sending the command from thecontroller to the memory device in response to receiving the command atthe controller.
 17. The method of claim 16, further comprisingtransferring data between the memory device and the host in response toreceiving the command.
 18. The method of claim 16, further comprisingtransferring data between the memory device and a different memorydevice in response to receiving the command.
 19. The method of claim 16,further comprising sending a signal from the memory device to thecontroller in response to executing the command.
 20. The method of claim16, further comprising storing data associated with the command in thememory device or in a different memory device.